allow passing hf_token to load_textual_inversion #10546
Merged
+4
−4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Cc: @yiyixuxu WDYT? |
|
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
|
thanks! can we update the docstring here accordingly? |
Teriks
force-pushed
the
load_textual_inversion_hf_token_fix
branch
from
f31c0a8 to
583164a
Compare
synced fork and double checked that on line 315 of the diff |
Teriks
added a commit
to Teriks/dgenerate
that referenced
this pull request
Apr 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allows passing HF_TOKEN to load_textual_inversion explicitly using the argument
hf_tokenas suggested in the linked issue.Fixes duplicate parameter name conflict caused by kwargs usage, as
tokenis used by this method to denote a lexical token and not an authentication token.Fixes #7689
Before submitting
documentation guidelines, and
here are tips on formatting docstrings.
Who can review?
@sayakpaul